-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: add --no-workspaces to npm whoami #529
base: master
Are you sure you want to change the base?
Conversation
This would be a welcome change, as I'm also blocked by the current behavior. |
Since I use |
we are pretty strongly against adding code to core or official plugins that is specifically for projects that are monorepos. if someone would like to send us PRs, we are happy to better document workarounds like using npmrc, publishConfig in the package.json, or npm environment variables that can enable these sorts of things without changes to semantic-release. if someone knows a solution to this issue without adding a flag, please let us know. adding things like this add extra complexity to the project that we have to maintain and not break over time that are only there for unsupported use cases. we have a hard enough time keeping up with the use cases we do officially support. we do try to avoid doing things specifically to prevent use in monorepos, but we do not support them officially so priority is very low if changes are needed to the official projects to enable that to work beyond what the community provides to extend the official projects. |
@travi I see. As far as this issue goes, it seems like FWIW, I've been using |
I'm using semantic-release with a monorepo which is not officially supported but discussed (e.g. semantic-release/semantic-release#1688).
I've tried various alternative but each of them gave me an uncomfortable feeling and after reading through #482 I settled with the seemingly simple option of only using semantic-release together with this
.npmrc
:There's currently one issue blocking me from using this approach. Executing
npm whoami
with the above.npmrc
yields an error, described in #470.This issue could be resolved by modifying
lib/verify-auth.js
slightly:The NPM docs mention:
I have verified that this flag has no adverse effect, running it on monorepos and non-monorepos both with and without the flag yield the same output.